Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1102

reference: 754-tree-1
name: 1102
tree-preservation-order: undefined
754-tpo-1
uprn
address-text
point: POINT (-1.011167 50.888347)
geometry: MULTIPOLYGON (((-1.011111 50.888341,-1.011113 50.888352,-1.011121 50.888362,-1.011133 50.888370,-1.011149 50.888375,-1.011167 50.888377,-1.011184 50.888376,-1.011200 50.888371,-1.011213 50.888363,-1.011221 50.888353,-1.011224 50.888342,-1.011222 50.888331,-1.011214 50.888321,-1.011202 50.888313,-1.011186 50.888307,-1.011168 50.888305,-1.011151 50.888307,-1.011135 50.888312,-1.011122 50.888320,-1.011114 50.888330,-1.011111 50.888341)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL